Intelligent drone traffic management via radio access network

ABSTRACT

Concepts and technologies disclosed herein are directed to intelligent drone traffic management via a radio access network (“RAN”). As disclosed herein, a RAN node, such as an eNodeB, can receive, from a drone, a flight configuration. The flight configuration can include a drone ID and a drone route. The RAN node can determine whether capacity is available in an airspace associated with the RAN node. In response to determining that capacity is available in the airspace associated with the RAN node, the RAN node can add the drone ID to a queue of drones awaiting use of the airspace associated with the RAN node. When the drone ID is next in the queue of drones awaiting use of the airspace associated with the RAN node, the RAN node can instruct the drone to fly through at least a portion of the airspace in accordance with the drone route.

RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto each of, U.S. patent application Ser. No. 17/194,485, filed Mar. 8,2021, and entitled “INTELLIGENT DRONE TRAFFIC MANAGEMENT VIA RADIOACCESS NETWORK,” which is a continuation of U.S. patent application Ser.No. 15/927,900 (now U.S. Pat. No. 10,977,952), filed Mar. 21, 2018, andentitled “INTELLIGENT DRONE TRAFFIC MANAGEMENT VIA RADIO ACCESSNETWORK,” which is a continuation of U.S. patent application Ser. No.14/929,858 (now U.S. Pat. No. 9,940,842), filed Nov. 2, 2015, andentitled “INTELLIGENT DRONE TRAFFIC MANAGEMENT VIA RADIO ACCESSNETWORK,” the entireties of which priority applications are herebyincorporated by reference herein.

BACKGROUND

Unmanned aerial vehicles (“UAVs”), commonly known as drones, includeaircraft capable of flight without a human pilot onboard. Drones come ina variety of shapes and sizes and utilize different designs to achieveflight. Drones are becoming increasingly popular in governmentoperations, civil operations, and even recreational/hobbyist use.Integrating drone flight with other aircraft and addressing safety andprivacy concerns are all topics currently being considered by local,state, and federal governments to ensure the benefit of drones in avariety of applications can be safely implemented into society.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating aspects of an illustrativeoperating environment for various concepts disclosed herein.

FIG. 2 is a block diagram illustrating aspects of an illustrative dronein communication with an illustrative eNode-B (“eNB”), according to anillustrative embodiment of the concepts and technologies disclosedherein.

FIG. 3 is a flow diagram illustrating aspects of a method for operatinga drone, according to an illustrative embodiment of the concepts andtechnologies disclosed herein.

FIGS. 4A-4B are flow diagrams illustrating aspects of a method foroperating an eNB, according to an illustrative embodiment of theconcepts and technologies disclosed herein.

FIG. 5 is a flow diagram illustrating aspects of a method for an eNBhandover process for managing a drone, according to an illustrativeembodiment of the concepts and technologies disclosed herein.

FIG. 6 is a block diagram illustrating an example computer systemcapable of implementing aspects of the embodiments presented herein.

FIG. 7 is a diagram illustrating a network, according to an illustrativeembodiment.

DETAILED DESCRIPTION

As a non-limiting overview, concepts and technologies disclosed hereinare directed to intelligent drone traffic management via a radio accessnetwork (“RAN”). According to one aspect of the concepts andtechnologies disclosed herein, a RAN node, such as an eNodeB, canreceive, from a drone, a flight configuration. The flight configurationcan include a drone ID and a drone route. The RAN node can determinewhether capacity is available in an airspace associated with the RANnode. In response to determining that capacity is available in theairspace associated with the RAN node, the RAN node can add the drone IDto a queue of drones awaiting use of the airspace associated with theRAN node. When the drone ID is next in the queue of drones awaiting useof the airspace associated with the RAN node, the RAN node can instructthe drone to fly through at least a portion of the airspace inaccordance with the drone route.

In some embodiments, the flight configuration also can include apriority flag indicating whether the drone is to be given priority inthe queue of drones awaiting use of the airspace associated with the RANnode. In these embodiments, the RAN node can, in response to determiningthat capacity is available in the airspace associated with the radioaccess network node, determine whether the drone is priority eligiblebased upon the priority flag; and, in response to determining that thedrone is priority eligible, the RAN node can prioritize the drone ID inthe queue.

In some embodiments, the RAN node can, in response to determining thedrone ID is not next in the queue, instruct the drone to enter a holdingpattern in a designated portion of the airspace associated with theradio access network node. The RAN node can release the drone from theholding pattern upon the drone ID becoming next in the queue. The queuecan schedule multiple drones per queue space so that being next in thequeue can constitute being one of a plurality of drones considered nextin the queue.

In some embodiments, the RAN node can, in response to determining thatcapacity is not available in the airspace associated with the RAN node,instruct the drone to proceed to a different RAN node. In theseembodiments, the RAN node can perform a handover of communications withthe drone to the different RAN node.

It should be appreciated that the above-described subject matter may beimplemented as a computer-controlled apparatus, a computer process, acomputing system, or as an article of manufacture such as acomputer-readable storage medium. These and various other features willbe apparent from a reading of the following further detailed descriptionand a review of the associated drawings.

The above overview is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This overview is not intended to identify key features oressential features of the claimed subject matter, nor is it intendedthat this overview be used to limit the scope of the claimed subjectmatter. Furthermore, the claimed subject matter is not limited toimplementations that solve any or all disadvantages noted in any part ofthis disclosure.

While the subject matter described herein may be presented, at times, inthe general context of program modules that execute in conjunction withthe execution of an operating system and application programs on acomputer system, those skilled in the art will recognize that otherimplementations may be performed in combination with other types ofprogram modules. Generally, program modules include routines, programs,components, data structures, computer-executable instructions, and/orother types of structures that perform particular tasks or implementparticular abstract data types. Moreover, those skilled in the art willappreciate that the subject matter described herein may be practicedwith other computer system, including hand-held devices, Drones,wireless devices, multiprocessor systems, distributed computing systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, routers, switches, other computingdevices described herein, and the like.

In the following further detailed description, references are made tothe accompanying drawings that form a part hereof, and in which areshown by way of illustration specific embodiments or examples. Referringnow to the drawings, in which like numerals represent like elementsthroughout the several figures, aspects of intelligent drone trafficmanagement via a RAN will be presented.

Referring now to FIG. 1 , aspects of an illustrative operatingenvironment 100 for various concepts disclosed herein will be described.It should be understood that the operating environment 100 and thevarious components thereof have been greatly simplified for purposes ofdiscussion. Accordingly, additional or alternative components of theoperating environment 100 can be made available without departing fromthe embodiments described herein.

The operating environment 100 shown in FIG. 1 includes a drone 102, alsoreferred to as an unmanned aerial vehicle (“UAV”). As used herein, a“drone” is defined as an unmanned aircraft that can navigateautonomously during flight. Autonomous flight is used herein to refer toflight without human control. In some embodiments, the drone 102 can beremotely controlled by a human user for flight testing, maintenance,emergency landings, or for other reasons. For example, the drone 102might include an operational setting that allows control to be handedover to a human. This control can be via line of sight or beyond line ofsight utilizing one or more cameras installed on the drone 102 forsight. Those skilled in the art will appreciate the wide range ofcontrol options suitable for controlling the drone 102 during theaforementioned use cases and others.

The drone 102 can be any shape and size, and can utilize any design toachieve flight. In some embodiments, the drone 102 is a fixed-wingaircraft. In some other embodiments, the drone 102 is a rotary-wingaircraft. In some other embodiments, the drone 102 is an ornithopter.Those skilled in the art will appreciate the wide range of propulsionsystems that can be utilized by the drone 102.

The drone 102 can perform flights for various use cases. It should beunderstood that the concepts and technologies disclosed herein are notlimited to any specific use case, and while some specific use cases arementioned herein, the concepts and technologies disclosed herein are notlimited thereto. Some common use cases include agriculture operations,forest health monitoring operations, firefighting operations, land andenvironment surveying operations, weather monitoring operations, trafficmonitoring operations, wildlife surveying operations, geologicalsurveying operations, structural inspection operations, search andrescue operations, delivery operations (e.g., food delivery, productdelivery, and the like), security operations, disaster responseoperations, and the like.

In the illustrated example, the drone 102 flies from a drone originlocation (“drone origin”) 104 to a drone destination location (“dronedestination”) 106. During the flight, the drone 102 can navigate intoeNB airspaces 108A-108N (collectively, “eNB airspaces 108”)corresponding to one or more eNBs 110A-110N (collectively, “eNBs 110”)operating as part of a RAN 112 as will be described in greater detailherein. The drone 102 can fly with or without a payload.

The drone origin 104 includes a drone origin system 114. The drone 102can communicate with the drone origin system 114 via a drone-originsystem connection 116 to receive a drone flight configuration 118 aspart of a pre-flight preparation process. The pre-flight preparationprocess can include programming the drone 102 with the drone flightconfiguration 118 via the drone-origin system connection 116. In someembodiments, the drone origin system 114 receives input from a user (notshown), wherein the input includes at least a portion of the droneflight configuration 118. In some other embodiments, the drone originsystem 114 automatically generates at least a portion of the droneflight configuration 118 based upon information provided by anapplication executing on the drone origin system 114 or another system(not shown). For example, a shipping application can receive input of adelivery address for a particular package.

The drone-origin system connection 116 can be a wired or wirelessconnection utilizing any standardized or proprietary connectionprotocol. Some example protocols include, but are not limited to, WI-FI,WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), nearfield communications (“NFC”), other RF technologies, Ethernet, UniversalSerial Bus (“USB”), and the like.

The drone origin system 114 can be or can include a computing device,such as a tablet computing device, a personal computer (“PC”), a desktopcomputer, a laptop computer, a notebook computer, a cellular phone orsmartphone, other mobile computing devices, a personal digital assistant(“PDA”), or the like. Example architectures of the drone origin system114 are illustrated and described herein below with reference to FIGS. 6and 7 . The functionality of the drone origin system 114 can beprovided, at least in part, by a cloud-based computing platform that canbe provided by one or more application servers, web servers, datastorage systems, network appliances, dedicated hardware devices, and/orother server computers or computing devices, which might, in someembodiments, leverage compute, memory, and/or other resources of avirtualization platform to perform operations described herein. In lightof the above alternative embodiments of the drone origin system 114, itshould be understood that this example is illustrative and should not beconstrued as being limiting in any way.

The illustrated drone flight configuration 118 includes a drone ID 120,a drone route 122, and a priority flag 124. The drone ID 120 is used touniquely identify the drone 102. In some embodiments, the drone ID 120is a temporary identifier assigned by the drone origin system 114 forone or more flights. In some other embodiments, the drone ID 120 is apermanent identifier assigned by the drone origin system 114, amanufacturer, or another entity. The drone ID 120 can include one ormore letters, one or more numbers, one or more characters, one or morepunctuation marks, one or more symbols, any combination thereof, and/orthe like. In some embodiments, the drone ID 120 includes a permanentuser equipment (“UE”) identifier, such as an International MobileSubscriber Identity (“IMSI”) and/or an International Mobile EquipmentIdentity (“IMEI”).

The drone route 122 includes a route from the drone origin 104 to thedrone destination 106. The drone route 122 can include two or morewaypoints, including a start waypoint (such as a location that includesthe drone origin 104), a finish waypoint (such as a location thatincludes the drone destination 106), and, optionally, one or more enroute waypoints (such as one or more of the locations in which the eNBs110 reside). The waypoints can be Global Positioning System (“GPS”)waypoints described in terms of latitude and longitude coordinates andan altitude. Moreover, a waypoint can include a range of latitudecoordinates, a range of longitude coordinates, a range of altitudes, orsome combination thereof. In some embodiments, the waypoints correspondto the eNBs 110 such that, for example, the drone route 122 consists ofa series of hops from the eNB₁ 110A to the eNB₂ 110B to the eNB_(N)110N.

The priority flag 124 includes an indication of whether or not the drone102 should be given priority over one or more other drones (not shown)for access to the eNB airspaces 108A-108N corresponding to the eNBs110A-110N, respectively. The airspaces 108A-108N can include any areaserved by the eNBs 110A-110N, respectively. For example, the typicalrange of an eNB in accordance with current Long-Term Evolution (“LTE”)standards is between two and three miles radially. Vertical coverage istypically less and may reduce the coverage area that constitutes the eNBairspaces 108A-108N. In some embodiments, one or more of the eNBs 110can be configured or modified to support greater lateral and/or verticalcoverage via antenna modifications (e.g., raising the height of theantenna or increasing the available power), changing frequencies, and/orother configurations/modifications those skilled in the art wouldappreciate to increase the coverage area radially and/or vertically.

The illustrated drone destination 106 includes a drone destinationsystem 126 that can interact with the drone 102, via a drone-destinationsystem connection 128, to access the drone flight configuration 118. Thedrone destination system 126 also can access a flight summary (notshown) that can include, for example, data collected during the flight(e.g., speed, altitude, and/or other sensor data; audio, video, and/orstill images; battery utilization; and the like). The drone-destinationsystem connection 128 can be a wired or wireless connection utilizingany standardized or proprietary connection protocol. Some exampleprotocols include, but are not limited to, WI-FI, WIMAX, BLUETOOTH,infrared, IRDA, NFC, other RF technologies, Ethernet, USB, and the like.

The drone destination system 126 can be or can include a computingdevice, such as a tablet computing device, a PC, a desktop computer, alaptop computer, a notebook computer, a cellular phone or smartphone,other mobile computing devices, a PDA, or the like. Examplearchitectures of the drone destination system 126 are illustrated anddescribed herein below with reference to FIGS. 6 and 7 . Thefunctionality of the drone destination system 126 can be provided, atleast in part, by a cloud-based computing platform that can be providedby one or more application servers, web servers, data storage systems,network appliances, dedicated hardware devices, and/or other servercomputers or computing devices, which might, in some embodiments,leverage compute, memory, and/or other resources of a virtualizationplatform to perform operations described herein. In light of the abovealternative embodiments of the drone destination system 126, it shouldbe understood that this example is illustrative and should not beconstrued as being limiting in any way.

The drone destination system 126 can function as the drone origin system114, or vice versa depending upon whether the system is functioning asthe destination or origin for the drone 102. For example, after arrivalat the drone destination 106, the drone 102″″ can receive a new routefrom the drone destination system 126 that is functioning as an originsystem. In other words, the terms “origin” and “destination” for thesystems 114/126 are dependent upon the drone route 122 and do notnecessarily limit the functionality to operations described herein asbeing performed, in particular, by the drone origin system 114 or thedrone destination system 126.

The RAN 112 can include one or more service areas (which may also bereferred to herein as “cells”) having the same or different cell sizes,which may be represented by different cell-types. As used herein, a“cell” refers to a geographical area that is served by one or more basestations, such as the eNBs 110, operating within an access network. Thecells within the RAN 112 can include the same or different cell sizes,which may be represented by different cell-types. A cell-type can beassociated with certain dimensional characteristics that define theeffective radio range of a cell. Cell-types can include, but are notlimited to, a macro cell-type, a metro cell-type, a femto cell-type, apico cell-type, a micro cell-type, wireless local area network (“WLAN”)cell-type, a MSMC cell-type, and a white space network cell-type. Forease of explanation, a “small cell” cell-type is utilized herein tocollectively refer to a group of cell-types that includes femtocell-type (e.g., home eNB), pico cell-type, and micro cell-type, ingeneral contrast to a macro cell-type, which offers a larger coveragearea. Other cell-types, including proprietary cell-types and temporarycell-types are also contemplated.

The RAN 112 might operate in accordance with one or more mobiletelecommunications standards including, but not limited to, GlobalSystem for Mobile communications (“GSM”), Code Division Multiple Access(“CDMA”) ONE, CDMA2000, Universal Mobile Telecommunications System(“UMTS”), LTE, Worldwide Interoperability for Microwave Access(“WiMAX”), other current 3GPP cellular technologies, other future 3GPPcellular technologies, combinations thereof, and/or the like. The RAN112 can utilize various channel access methods (which may or may not beused by the aforementioned standards), including, but not limited to,Time Division Multiple Access (“TDMA”), Frequency Division MultipleAccess (“FDMA”), CDMA, wideband CDMA (“W-CDMA”), Orthogonal FrequencyDivision Multiplexing (“OFDM”), Single-Carrier FDMA (“SC-FDMA”), SpaceDivision Multiple Access (“SDMA”), and the like to provide a radio/airinterface to the drone 102. Data communications can be provided in partby the RAN 112 using General Packet Radio Service (“GPRS”), EnhancedData rates for Global Evolution (“EDGE”), the High-Speed Packet Access(“HSPA”) protocol family including High-Speed Downlink Packet Access(“HSDPA”), Enhanced Uplink (“EUL”) or otherwise termed High-Speed UplinkPacket Access (“HSUPA”), Evolved HSPA (“HSPA+”), LTE, and/or variousother current and future wireless data access technologies. Moreover,the RAN 112 may be a GSM RAN (“GRAN”), a GSM EDGE RAN (“GERAN”), a UNITSTerrestrial Radio Access Network (“UTRAN”), an evolved U-TRAN(“E-UTRAN”), any combination thereof, and/or the like.

As used herein, a “base station” refers to a radio receiver and/ortransmitter (collectively, transceiver) that is/are configured toprovide a radio/air interface over which one or more drones, such as thedrone 102, can connect to a network. Accordingly, a base station isintended to encompass one or more base transceiver stations (“BTSs”),one or more NBs, one or more eNBs, one or more home eNBs, one or morewireless access points (“APs”), one or more multi-standard metro cell(“MSMC”) nodes, and/or other networking nodes or combinations thereofthat are capable of providing a radio/air interface regardless of thetechnologies utilized to do so. A base station can be in communicationwith one or more antennas (not shown), each of which may be configuredin accordance with any antenna design specifications to provide aphysical interface for receiving and transmitting radio waves to andfrom one or more devices, such as the drone 102. The illustratedembodiment shows base stations embodied as the eNBs 110. This embodimentis illustrative and should not be construed as being limiting in anyway.

In the illustrated embodiment, the eNB₁ 110A is shown with a dronetraffic management database 130. The drone traffic management database130 can store a drone capacity 132, a number of active drones 134, oneor more drone IDs for active drone(s) (“active drone ID(s)”) 136, and adrone queue 138. The drone capacity 132 includes a maximum number ofdrones that can operate within an associated airspace (in theillustrated example, the eNB₁ airspace 108A). The number of activedrones 134 includes a current number of drones operating within theassociated airspace. The active drone ID(s) 136 includes the drone ID(s)for the active drone(s). For example, if the drone 102 is the only droneoperating within the eNB₁ 110A, the number of active drones 134 can beset to one and the active drone ID(s) 136 can include the drone ID 120.The drone queue 138 includes a queue of one or more drone IDs associatedwith drones that are awaiting entry into the eNB₁ airspace 108A. In someembodiments, queued drones can be instructed to enter a holding patternin a designated portion of the eNB₁ airspace 108A. The eNB₂ 110B and theeNBN 110N each can include an instance of the drone traffic managementdatabase 130 particular thereto. As such, the drone capacity 132, thenumber of active drones 134, the active drone ID(s) 136, and the dronequeue 138 can differ among the eNBs 110.

When the drone 102 arrives in one of the airspaces 108, the drone 102sends the drone flight configuration 118 to the associated one of theeNBs 110. In the illustrated example, the drone 102 leaves the droneorigin 104 and arrives in the eNB₁ airspace 108A (illustrated as thedrone 102′). The drone 102′ provides the drone flight configuration 118to the eNB₁ 110A, and in response, the eNB₁ 110A can generate a set offlight instructions 140 utilized by the eNB₁ 110A to instruct the drone102′ regarding how to proceed during the flight. The set of flightinstructions 140 can instruct the drone 102′ to enter a holding patternuntil further notice. The set of flight instructions 140 can instructthe drone 102′ to fly through at least a portion of the eNB₁ airspace108A in accordance with the drone route 122. The set of flightinstructions 140 can instruct the drone 102′ to fly to a differentairspace, such as, in the illustrated example, the eNB₂ airspace 108B.In the illustrated example, the drone 102′ leaves the eNB₁ airspace 108Aand arrives in the eNB₂ airspace 108B (illustrated as the drone 102″).In this scenario, the eNB₁ 110A can handover communications with thedrone 102′ to the eNB₂ 110B (shown generally as drone HO₁ 142A), andsimilarly, the eNB₂ 110B can handover communications with the drone 102″to the eNB_(N) 110N (shown generally as drone HO₂ 142B) when the drone102″ leaves the eNB₂ airspace 108B and arrives in the eNB_(N) airspace108N (illustrated as the drone 102′″).

The RAN 112 is shown as being in communication with an evolved packetcore (“EPC”) network 144. The EPC network 144 can include one or moremobility management entities (“MME”; not shown), one or more servinggateways (“SGWs”; not shown), one or more packet data networks (“PDN”)gateways (“PGWs”; not shown), and one or more home subscriber servers(“HSSs”; not shown). An MME controls signaling related to mobility andsecurity for E-UTRAN access, such as via the RAN 112, by the drone 102as well as other UEs, such as mobile phones, tablets, and the like (notshown). The SGW(s) provides a point of interconnect between theradio-side (e.g., the RAN 112) and the EPC network 144. An SGW servesthe drone 102 (and other drones and UEs not shown) by routing incomingand outgoing IP packets. A PGW interconnects the EPC network 144 and oneor more external IP networks, shown in the illustrated embodiment as aPDN 146. A PGW routes IP packets to and from the PDN 146. A PGW alsoperforms operations such as IP address/IP prefix allocation, policycontrol, and charging. In some implementations, a PGW and an SGW arecombined. An HSS is a database that contains user/subscriberinformation. An HSS also performs operations to support mobilitymanagement, call and session setup, user authentication, and accessauthorization.

It should be understood that some implementations of the operatingenvironment 100 include multiple drones 102, multiple drone origins 104,multiple drone destinations 106, one or more RANs 112, one or more droneorigin systems 114, one or more drone-origin system connections 116, oneor more drone flight configurations 118, one or more drone IDs 120, oneor more drone routes 122, one or more priority flags 124, one or moredrone destination systems 126, one or more drone-destination systemconnections 128, one or more drone traffic management database 130, oneor more drone queues 138, one or more sets of flight instructions 140,one or more EPC networks 144, one or more PDNs 146, or some combinationthereof. Thus, the illustrated embodiment should be understood as beingillustrative, and should not be construed as being limiting in any way.

Turning now to FIG. 2 , a block diagram illustrating aspects (generallyshown at 200) of an illustrative drone, such as the drone 102, incommunication with an illustrative eNB, such as one of the eNBs 110,will be described according to an illustrative embodiment of theconcepts and technologies disclosed herein. The illustrated drone 102includes one or more drone processors 202, one or more drone memorycomponents 204, one or more drone input/output (“I/O”) components 206,one or more drone RAN components 208, one or more drone operatingsystems 210, a flight control application 212, and a drone networkconnection manager 214.

The drone processor(s) 202 can include a central processing unit (“CPU”)configured to process data, execute computer-executable instructions ofone or more application programs, and communicate with other componentsof the drone 102 in order to perform various functionality describedherein. The drone processor(s) 202 may be utilized to execute aspects ofthe drone operating system(s) 210 and the flight control application212. In some embodiments, the drone processor(s) 202 is, or is includedin, a system-on-chip (“SoC”) along with one or more of the othercomponents described herein below. For example, the SoC may include thedrone processor(s) 202, a GPU, and the drone RAN component(s) 208. Insome embodiments, the drone processor 200 is fabricated, in part,utilizing a package-on-package (“PoP”) integrated circuit packagingtechnique. Moreover, the drone processor(s) 202 may be a single core ormulti-core processor. The drone processor(s) 202 may be created inaccordance with an ARM architecture, available for license from ARMHOLDINGS of Cambridge, United Kingdom. Alternatively, the droneprocessor(s) 202 may be created in accordance with an x86 architecture,such as is available from INTEL CORPORATION of Mountain View, Calif. andothers. In some embodiments, the drone processor(s) 202 is a SNAPDRAGONSoC, available from QUALCOMM of San Diego, Calif., a TEGRA SoC,available from NVIDIA of Santa Clara, Calif., a HUMMINGBIRD SoC,available from SAMSUNG of Seoul, South Korea, an Open MultimediaApplication Platform (“OMAP”) SoC, available from TEXAS INSTRUMENTS ofDallas, Tex., a customized version of any of the above SoCs, or aproprietary SoC.

The drone memory component(s) 204 can include a random access memory(“RAM”), a read-only memory (“ROM”), an integrated storage memory(“integrated storage”), and a removable storage memory (“removablestorage”), or some combination thereof. In some embodiments, the dronememory component(s) 204 are included as part of the drone processor(s)202. In some embodiments, the drone memory component(s) 204 store thedrone operating system(s) 210 or a portion thereof (e.g., operatingsystem kernel or bootloader), the flight control application 212, andthe drone network connection manager 214.

The drone network connection manager 214 can manage all or a portion ofthe network connections available to the drone 102 at a given time. Thenetwork connections can include, for example, connections establishedvia the drone RAN components 208, which may be or may include one ormore cellular radios and/or other radios suited for the radio accesstechnologies described herein above. In some embodiments, the dronenetwork connection manager 214 is included as part of the droneoperating system(s) 210.

The drone operating system 210 is a program for controlling theoperation of the drone 102. The drone operating system 210 can include aproprietary operating system, an embedded operating system, a member ofthe SYMBIAN OS family of operating systems from SYMBIAN LIMITED, amember of the WINDOWS MOBILE OS and/or WINDOWS PHONE OS families ofoperating systems from MICROSOFT CORPORATION, a member of the PALM WEBOS family of operating systems from HEWLETT PACKARD CORPORATION, amember of the BLACKBERRY OS family of operating systems from RESEARCH INMOTION LIMITED, a member of the IOS family of operating systems fromAPPLE INC., a member of the ANDROID OS family of operating systems fromGOOGLE INC., and/or other operating systems. These operating systems aremerely illustrative of some contemplated operating systems that may beused in accordance with various embodiments of the concepts andtechnologies described herein and therefore should not be construed asbeing limiting in any way.

The flight control application 212 is an application executable by thedrone processor(s) 202 to control flight of the drone 102. The flightcontrol application 212 can utilize the drone flight configuration 118and the set of flight instructions (“flight instructions”) 140 receivedfrom the eNB 110 to determine the trajectory of the drone 102 andmanipulate various mechanical components (not shown) of the drone 102 toenable flight. The flight control application 212 also can provide aninterface through which the drone origin system 114 and the dronedestination system 126 can communicate with the drone 102. For example,the drone flight configuration 118 can be loaded onto the drone 102 viathe flight control application 212.

The illustrated eNB 110 includes one or more eNB processors 216, one ormore eNB memory components 218, a baseband unit (“BBU”) 220, one or moreremote radio heads (“RRHs”) 222, one or more eNB operating systems 224,and one or more eNB applications 226. Each of these components will nowbe described in detail.

The eNB processor(s) 216 can include one or more processing unitsconfigured to process data, execute computer-executable instructions ofone or more application programs, and communicate with other componentsof the eNB 110 in order to perform various functionality describedherein. The eNB processor(s) 216 may be utilized to execute aspects ofthe eNB operating system(s) 224 and the eNB application(s) 226. In someembodiments, the eNB processor(s) 216 is or includes a CPU, acommunications processor, or a FPGA. In some embodiments, the eNBprocessor(s) 216 is, or is included in, a SoC along with one or more ofthe other components described herein below. For example, the SoC mayinclude the eNB processor(s) 216, a GPU, the BBU 220, the RRH(s) 222, orsome combination thereof. In some embodiments, the eNB processor(s) 216is fabricated, in part, utilizing a PoP integrated circuit packagingtechnique. Moreover, the eNB processor(s) 216 may be a single core ormulti-core processor. The eNB processor(s) 216 may be created inaccordance with an ARM architecture, available for license from ARMHOLDINGS of Cambridge, United Kingdom. Alternatively, the eNBprocessor(s) 216 may be created in accordance with an x86 architecture,such as is available from INTEL CORPORATION of Mountain View, Calif. andothers. In some embodiments, the eNB processor(s) 216 is a SNAPDRAGONSoC, available from QUALCOMM of San Diego, Calif., a TEGRA SoC,available from NVIDIA of Santa Clara, Calif., a HUMMINGBIRD SoC,available from SAMSUNG of Seoul, South Korea, an OMAP SoC, availablefrom TEXAS INSTRUMENTS of Dallas, Tex., a customized version of any ofthe above SoCs, or a proprietary SoC.

The eNB memory component(s) 218 can include a RAM, a ROM, an integratedstorage memory, and a removable storage memory, or some combinationthereof. In some embodiments, the eNB memory component(s) 218 areincluded as part of the eNB processor(s) 216. In some embodiments, theeNB memory component(s) 218 store the eNB operating system(s) 224 or aportion thereof (e.g., operating system kernel or bootloader), the eNBapplication(s) 226, and the drone traffic management database 130.

The BBU 220 is the baseband processing unit of the eNB 110. The BBU 220can include other components shown, including, for example, the eNBprocessor(s) 216, the eNB memory component(s) 218, the eNB operatingsystem(s) 224, the eNB application(s) 226, or some combination thereof.The BBU 220 can receive IP packets received from the EPC network 144(shown in FIG. 1 ) and can modulate the IP packets into digital basebandsignals. The BBU 220 can send the digital baseband signals to the RRH(s)222. The digital baseband signals received from the RRH(s) 222 aredemodulated and IP packets are transmitted to the EPC network 144. TheRRH(s) 222 can transmit and receive wireless signals from the drone 102,including, for example, a signal carrying the drone flight configuration118 and a signal carrying the flight instructions 140. The RRH(s) 222also convert the digital baseband signals from the BBU 220 that havebeen subjected to protocol-specific processing into RF signals and poweramplifies the signals for transmission to the drone 102. The RF signalsreceived from the drone 102 are amplified and converted to digitalbaseband signals for transmission to the BBU 220.

The eNB operating system(s) 224 is a program for controlling theoperation of the eNB 110. The eNB operating system(s) 224 can include aproprietary operating system, an embedded operating system, a member ofthe SYMBIAN OS family of operating systems from SYMBIAN LIMITED, amember of the WINDOWS MOBILE OS and/or WINDOWS PHONE OS families ofoperating systems from MICROSOFT CORPORATION, a member of the PALM WEBOS family of operating systems from HEWLETT PACKARD CORPORATION, amember of the BLACKBERRY OS family of operating systems from RESEARCH INMOTION LIMITED, a member of the IOS family of operating systems fromAPPLE INC., a member of the ANDROID OS family of operating systems fromGOOGLE INC., and/or other operating systems. These operating systems aremerely illustrative of some contemplated operating systems that may beused in accordance with various embodiments of the concepts andtechnologies described herein and therefore should not be construed asbeing limiting in any way.

The eNB application(s) 226 can be any application that performsoperations for the eNB 110. For example, the eNB application(s) 226 canbe or can include software compliant with 3GPP standards for callcontrol processing, performance management, self-organizing networkfunctions, and the like. The eNB application(s) 226 also can be or caninclude software for interacting with the drone 102, including softwarefor generating the flight instructions 140. Additional details regardingoperations that can be performed by the eNB application(s) 226 aredescribed herein with regard to FIGS. 4A, 4B, and 5 .

Turning now to FIG. 3 , a flow diagram illustrating aspects of a method300 for operating a drone, such as the drone 102, will be described,according to an illustrative embodiment. It should be understood thatthe operations of the methods disclosed herein are not necessarilypresented in any particular order and that performance of some or all ofthe operations in an alternative order(s) is possible and iscontemplated. The operations have been presented in the demonstratedorder for ease of description and illustration. Operations may be added,omitted, and/or performed simultaneously, without departing from thescope of the concepts and technologies disclosed herein.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions includedon a computer storage media, as defined herein. The term“computer-readable instructions,” and variants thereof, as used herein,is used expansively to include routines, applications, applicationmodules, program modules, programs, components, data structures,algorithms, and the like. Computer-readable instructions can beimplemented on various system configurations including single-processoror multiprocessor systems or devices, minicomputers, mainframecomputers, personal computers, hand-held computing devices,microprocessor-based, programmable consumer electronics, combinationsthereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These states, operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof. As used herein, the phrase “cause aprocessor to perform operations” and variants thereof is used to referto causing one or more processors of the drone 102, the eNBs 110, thedrone origin system 114, the drone destination system 126, and/or one ormore other computing systems and/or devices disclosed herein to performoperations.

For purposes of illustrating and describing some of the concepts of thepresent disclosure, the methods disclosed herein are described as beingperformed, in part, by the drone 102, the eNBs 110, the drone originsystem 114, and/or the drone destination system 126, via execution ofone or more software modules. It should be understood that additionaland/or alternative devices and/or network nodes can provide thefunctionality described herein via execution of one or more modules,applications, and/or other software. Thus, the illustrated embodimentsare illustrative, and should not be viewed as being limiting in any way.

The method 300 will be described with reference to FIG. 1 and furtherreference to FIG. 3 . The method 300 begins and proceeds to operation302, where the drone 102 and the drone origin system 114 establish aconnection (i.e., the drone-origin system connection 116) over which thedrone origin system 114 can configure the drone 102 for flight to thedrone destination 106. From operation 302, the method 300 proceeds tooperation 304, where the drone 102 receives the drone flightconfiguration 118 from the drone origin system 114. From operation 304,the method 300 proceeds to operation 306, where the drone 102 stores thedrone flight configuration 118.

From operation 306, the method 300 proceeds to operation 308, where thedrone 102 launches the flight control application 212 and loads thedrone route 122 from the drone flight configuration 118. From operation308, the method 300 proceeds to operation 310, where the drone 102 takesflight in accordance with the drone route 122.

From operation 310, the method 300 proceeds to operation 312, where thedrone 102 connects to the eNB₁ 110A. From operation 312, the method 300proceeds to operation 314, where the drone 102 provides the drone flightconfiguration 118 to the eNB₁ 110A. From operation 314, the method 300proceeds to operation 316, where the drone 102 receives the flightinstructions 140 from the eNB₁ 110A. From operation 316, the method 300proceeds to operation 318, where the drone 102 continues flight inaccordance with the flight instructions 140.

From operation 318, the method 300 proceeds to operation 320, where thedrone 102 connects to the eNB_(N) 110N. From operation 320, the method300 proceeds to operation 322, where the drone 102 determines whetherthe destination specified in the drone route 122 has been reached. Ifthe drone 102 determines that the destination has not been reached, themethod 300 proceeds to operation 324, where the drone 102 provides thedrone route 122 to the eNB_(N) 110N. From operation 324, the method 300proceeds to operation 326, where the drone 102 receives the flightinstructions 140 from the eNB_(N) 110N. From operation 326, the method300 proceeds to operation 328, where the drone 102 continues the flightin accordance with the flight instructions 140 provided by eNB_(N) 110N.From operation 328, the method 300 returns to operation 322. Operations322-328 are repeated until the drone 102 reaches the drone destination106.

When the drone 102 reaches the drone destination 106, the method 300proceeds from operation 322 to operation 330, where the drone 102 andthe drone destination system 126 establish a connection (i.e., thedrone-destination system connection 128. From operation 330, the method300 proceeds to operation 332, where the drone 102 provides a flightsummary to the drone destination system 126. From operation 332, themethod 300 proceeds to operation 334, where the method 300 ends.

Turning now to FIG. 4 , and first to FIG. 4A, a method 400 for operatingan eNB, such as one of the eNBs 110, will be described, according to anillustrative embodiment. The method 400 will described with reference toFIG. 4 and further reference to FIG. 1 .

The method 400 begins and proceeds to operation 402, where the eNB 110connects to the drone 102. From operation 402, the method 400 proceedsto operation 404, where the eNB 110 receives, from the drone 102, thedrone flight configuration 118, including the drone ID 120, the droneroute 122, and the priority flag 124.

From operation 404, the method 400 proceeds to operation 406, where theeNB 110 determines whether capacity is available to accommodate thedrone 102 in the airspace 108. If the eNB 110 determines that capacityis available, the method 400 proceeds to operation 408, where the eNB110 adds the drone ID 120 to the drone queue 138. From operation 408,the method 400 proceeds to operation 410, where the eNB 110 determineswhether the drone 102 is priority eligible based upon the priority flag124. If the eNB 110 determines that the drone 102 is priority eligible,the method 400 proceeds to operation 412, where the eNB 110 prioritizesthe drone ID 120 in the drone queue 138. From operation 412, the method400 proceeds to operation 414, which is shown in FIG. 4B. Also, if, atoperation 410, the eNB 110 determines that the drone 102 is not priorityeligible, the method 400 proceeds directly to operation 414.

At operation 414, the eNB 110 determines whether the drone ID 120 isnext in the drone queue 138. If the eNB 110 determines that the drone ID120 is not next in the drone queue 138, the method 400 proceeds tooperation 416, where the eNB 110 instructs, via the flight instructions140, the drone 102 to enter a holding pattern. From operation 416, themethod 400 returns to operation 414. If the eNB 110 determines that thedrone ID 120 is next in the drone queue 138, the method 400 proceeds tooperation 418, where the eNB 110 generates the flight instructions 140for the drone 102 to proceed along the drone route 122. From operation418, the method 400 proceeds to operation 420, where the eNB 110provides, to the drone 102, the flight instructions 140. From operation420, the method 400 proceeds to operation 422, where the method 400ends.

Returning to FIG. 4A, and particularly, to operation 406, the method 400proceeds to operation 424, where the eNB 110 generates the flightinstructions 140 for the drone 102 to proceed to a different eNB (e.g.,the eNB₂ 110B or the eNB_(N) 110N). From operation 424, the method 400returns to FIG. 4B, and particularly, to operation 420, where the eNB110 provides the flight instructions 140 to the drone 102. Fromoperation 420, the method 400 proceeds to operation 422, where themethod 400 ends.

Turning now to FIG. 5 , a flow diagram illustrating aspects of a method500 for an eNB handover process, such as the drone HO₁ 142A, formanaging a drone, such as the drone 102, will be described, according toan illustrative embodiment. The method 500 will described with referenceto FIG. 5 and further reference to FIG. 1 . The method 500 begins andproceeds to operation 502, where the eNB₁ 110A provides the flightinstructions 140 to the drone 102 to proceed to the eNB₂ airspace 108Bassociated with the eNB₂ 110B. From operation 502, the method 500proceeds to operation 504, where the eNB 110 performs the drone HO₁ 142Ato the eNB₂ 110B. From operation 504, the method 500 proceeds tooperation 506, where the method 500 ends.

Turning now to FIG. 6 , a block diagram illustrating a computer system600 configured to perform various operations disclosed herein. Thecomputer system 600 includes a processing unit 602, a memory 604, one ormore user interface devices 604, one or more input/output (“I/O”)devices 608, and one or more network devices 610, each of which isoperatively connected to a system bus 612. The system bus 612 enablesbi-directional communication between the processing unit 602, the memory604, the user interface devices 604, the I/O devices 608, and thenetwork devices 610. In some embodiments, one or more components of theRAN 112, the eNBs 110A-108N, the EPC network 144, one or more componentsof the PDN 146, the drone origin system 114, the drone destinationsystem 126, or some combination thereof is/are configured, at least inpart, like the computer system 600. It should be understood, however,that one or more components of the RAN 112, the eNBs 110A-108N, the EPCnetwork 144, one or more components of the PDN 146, the drone originsystem 114, and/or the drone destination system 126 may includeadditional functionality or include less functionality than nowdescribed.

The processing unit 602 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the computer system 600. Processingunits are generally known, and therefore are not described in furtherdetail herein.

The memory 604 communicates with the processing unit 602 via the systembus 612. In some embodiments, the memory 604 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 602 via the system bus 612. The illustrated memory 604includes an operating system 614 and one or more applications 614.

The operating system 614 can include, but is not limited to, members ofthe WINDOWS, WINDOWS CE, WINDOWS MOBILE, and/or WINDOWS PHONE familiesof operating systems from MICROSOFT CORPORATION, the LINUX family ofoperating systems, the SYMBIAN family of operating systems from SYMB IANLIMITED, the BREW family of operating systems from QUALCOMM CORPORATION,the MAC OS and/or iOS families of operating systems from APPLE INC., theFREEBSD family of operating systems, the SOLARIS family of operatingsystems from ORACLE CORPORATION, other operating systems such asproprietary operating systems, and the like.

The user interface devices 604 may include one or more devices withwhich a user accesses the computer system 600. The user interfacedevices 604 may include, but are not limited to, computers, servers,personal digital assistants, telephones (e.g., cellular, IP, orlandline), or any suitable computing devices. The I/O devices 608 enablea user to interface with the program modules. In one embodiment, the I/Odevices 608 are operatively connected to an I/O controller (not shown)that enables communication with the processing unit 602 via the systembus 612. The I/O devices 608 may include one or more input devices, suchas, but not limited to, a keyboard, a mouse, or an electronic stylus.Further, the I/O devices 608 may include one or more output devices,such as, but not limited to, a display screen or a printer.

The network devices 610 enable the computer system 600 to communicatewith other networks or remote systems via a network 618. Examples of thenetwork devices 610 include, but are not limited to, a modem, a radiofrequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface,a bridge, a router, or a network card. The network 618 may include awireless network such as, but not limited to, a WLAN such as a WI-FInetwork, a WWAN, a wireless PAN (“WPAN”) such as BLUETOOTH, or awireless MAN (“WMAN”). Alternatively, the network 618 may be a wirednetwork such as, but not limited to, a WAN such as the Internet, a LANsuch as the Ethernet, a wired PAN, or a wired MAN. The network 618 canbe or can include the RAN 112, the EPC network 144, and/or the PDN 146.

As used herein, communication media includes computer-executableinstructions, data structures, program modules, or other data in amodulated data signal such as a carrier wave or other transportmechanism and includes any delivery media. The term “modulated datasignal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared, and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

By way of example, and not limitation, computer storage media mayinclude volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer-executable instructions, data structures, program modules,or other data. For example, computer media includes, but is not limitedto, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memorytechnology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe drone 102, the eNBs 110, the drone origin system 114, or the dronedestination system 126 described herein. For purposes of the claims, thephrase “computer-readable storage medium” and variations thereof, doesnot include waves, signals, and/or other transitory and/or intangiblecommunication media, per se.

Encoding the software modules presented herein also may transform thephysical structure of the computer-readable media presented herein. Thespecific transformation of physical structure may depend on variousfactors, in different implementations of this description. Examples ofsuch factors may include, but are not limited to, the technology used toimplement the computer-readable media, whether the computer-readablemedia is characterized as primary or secondary storage, and the like.For example, if the computer-readable media is implemented assemiconductor-based memory, the software disclosed herein may be encodedon the computer-readable media by transforming the physical state of thesemiconductor memory. For example, the software may transform the stateof transistors, capacitors, or other discrete circuit elementsconstituting the semiconductor memory. The software also may transformthe physical state of such components in order to store data thereupon.

As another example, the computer-readable media disclosed herein may beimplemented using magnetic or optical technology. In suchimplementations, the software presented herein may transform thephysical state of magnetic or optical media, when the software isencoded therein. These transformations may include altering the magneticcharacteristics of particular locations within given magnetic media.These transformations also may include altering the physical features orcharacteristics of particular locations within given optical media, tochange the optical characteristics of those locations. Othertransformations of physical media are possible without departing fromthe scope and spirit of the present description, with the foregoingexamples provided only to facilitate this discussion. In light of theabove, it should be appreciated that many types of physicaltransformations may take place in the drone 102, the eNBs 110, the droneorigin system 114, or the drone destination system 126 in order to storeand execute the software components presented herein.

Turning now to FIG. 7 , details of a network 700 are illustrated,according to an illustrative embodiment. The network 700 includes acellular network 702 (e.g., the RAN 112 and the EPC network 144), apacket data network 704 (e.g., the PDN 146), and a circuit switchednetwork 706 (e.g., a public switched telephone network). The network 700can include the operating environment 100 illustrated and described withreference to FIG. 1 .

The cellular network 702 includes various components such as, but notlimited to, BTSs, NBs or eNBs (e.g., the eNBs 110A-110N), base stationcontrollers (“BSCs”), radio network controllers (“RNCs”), mobileswitching centers (“MSCs”), MMEs, short message service centers(“SMSCs”), multimedia messaging service centers (“MMSCs”), home locationregisters (“HLRs”), HSSs, visitor location registers (“VLRs”), chargingplatforms, billing platforms, voicemail platforms, GPRS core networkcomponents, location service nodes, and the like. The cellular network702 also includes radios and nodes for receiving and transmitting voice,data, and combinations thereof to and from radio transceivers, networks,the packet data network 704, and the circuit switched network 706. Amobile communications device 708 and the drone 102 can communicate withthe cellular network 702.

A mobile communications device 708, such as, for example, a cellulartelephone, a user equipment, a mobile terminal, a PDA, a laptopcomputer, a handheld computer, and combinations thereof, can beoperatively connected to the cellular network 702. The cellular network702 can be configured as a 2G GSM network and can provide datacommunications via GPRS and/or EDGE. Additionally, or alternatively, thecellular network 702 can be configured as a 3G UMTS network and canprovide data communications via the HSPA protocol family, for example,HSDPA, EUL (also referred to as HSUPA), and HSPA+. The cellular network702 also is compatible with 4G mobile communications standards such asLTE, or the like, as well as evolved and future mobile standards.

The packet data network 704 can include the PDN 146. The packet datanetwork 704 includes various devices, for example, servers, computers,databases, and other devices in communication with another, as isgenerally known. In some embodiments, the packet data network 704 is orincludes one or more WI-FI networks, each of which can include one ormore WI-FI access points, routers, switches, and other WI-FI networkcomponents. The packet data network 704 devices are accessible via oneor more network links. The servers often store various files that areprovided to a requesting device such as, for example, a computer, aterminal, a smartphone, or the like. Typically, the requesting deviceincludes software (a “browser”) for executing a web page in a formatreadable by the browser or other software. Other files and/or data maybe accessible via “links” in the retrieved files, as is generally known.In some embodiments, the packet data network 704 includes or is incommunication with the Internet. The circuit switched network 706includes various hardware and software for providing circuit switchedcommunications. The circuit switched network 706 may include, or may be,what is often referred to as a plain old telephone system (“POTS”). Thefunctionality of a circuit switched network 706 or othercircuit-switched network are generally known and will not be describedherein in detail.

The illustrated cellular network 702 is shown in communication with thepacket data network 704 and a circuit switched network 706, though itshould be appreciated that this is not necessarily the case. One or moreInternet-capable devices 710, for example, the drone 102, a PC, alaptop, a portable device, or another suitable device, can communicatewith one or more cellular networks 702, and devices connected thereto,through the packet data network 704. It also should be appreciated thatthe Internet-capable device 710 can communicate with the packet datanetwork 704 through the circuit switched network 706, the cellularnetwork 702, and/or via other networks (not illustrated).

As illustrated, a communications device 712, for example, a telephone,facsimile machine, modem, computer, or the like, can be in communicationwith the circuit switched network 706, and therethrough to the packetdata network 704 and/or the cellular network 702. It should beappreciated that the communications device 712 can be anInternet-capable device, and can be substantially similar to theInternet-capable device 710.

Based on the foregoing, it should be appreciated that concepts andtechnologies for intelligent drone traffic management via a RAN havebeen disclosed herein. Although the subject matter presented herein hasbeen described in language specific to computer structural features,methodological and transformative acts, specific computing machinery,and computer-readable media, it is to be understood that the variousembodiments defined in the appended claims are not necessarily limitedto the specific features, acts, or media described herein. Rather, thespecific features, acts and mediums are disclosed as example forms ofimplementing the claims.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of thesubject disclosure.

What is claimed is:
 1. A method, comprising: transmitting, by a dronedevice comprising a processor, to a first network node, a flightconfiguration for the drone device awaiting use of a first airspaceassociated with the first network node; and receiving, by the dronedevice, from the first network node based on a capacity constraint ofthe first airspace, an instruction for the drone device to leave thefirst airspace and proceed to a second airspace associated with a secondnetwork node.
 2. The method of claim 1, further comprising: in responseto receiving the instruction, navigating, by the drone device, to thesecond airspace.
 3. The method of claim 2, further comprising: inresponse to receiving the instruction, establishing, by the dronedevice, a communication link with the second network node.
 4. The methodof claim 1, wherein the flight configuration comprises a drone routeapplicable to the drone device and priority data representative of apriority associated with the drone device.
 5. The method of claim 1,wherein the capacity constraint is a function of a quantity of dronedevices operating in the first airspace.
 6. The method of claim 1, thecapacity constraint is defined with respect to an upper limit on aquantity of drone devices that are able to concurrently operate in thefirst airspace before instructing at least one of the drone devices toproceed to a different airspace other than the first airspace.
 7. Themethod of claim 1, wherein the capacity constraint is a function of apriority of the drone device.
 8. An unmanned aerial vehicle, comprising:a processor; and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations,comprising: sending, to a first network node, a flight configuration forthe unmanned aerial vehicle awaiting use of a first airspace associatedwith the first network node; and receiving, from the first network node,an instruction, based on a capacity constraint applicable to the firstairspace, for the unmanned aerial vehicle to leave the first airspaceand proceed to a second airspace associated with a second network node.9. The unmanned aerial vehicle of claim 8, wherein the operationsfurther comprise: in response to receiving the instruction, flying tothe second airspace.
 10. The unmanned aerial vehicle of claim 9, whereinthe operations further comprise: initiating establishment of a networkconnection with the second network node.
 11. The unmanned aerial vehicleof claim 8, wherein the flight configuration comprises a route and apriority associated with the unmanned aerial vehicle.
 12. The unmannedaerial vehicle of claim 8, wherein the capacity constraint is based on aquantity of unmanned aerial vehicles operating in the first airspace.13. The unmanned aerial vehicle of claim 8, the capacity constraintcomprises a constraint on a quantity of unmanned aerial vehicles thatare allowed to concurrently operate in the first airspace.
 14. Theunmanned aerial vehicle of claim 8, wherein the capacity constraint isbased on a priority of the unmanned aerial vehicle.
 15. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor of a drone device, facilitate performance ofoperations, comprising: sending, to a first network node, a flightconfiguration for the drone device awaiting use of a first airspaceassociated with the first network node; and based on a capacityconstraint of the first airspace being satisfied, receiving, from thefirst network node, an instruction for the drone device to leave thefirst airspace and proceed to a second airspace associated with a secondnetwork node.
 16. The non-transitory machine-readable medium of claim15, wherein the operations further comprise: in response to receivingthe instruction, flying to the second airspace.
 17. The non-transitorymachine-readable medium of claim 16, wherein the operations furthercomprise: in response to receiving the instruction, establishing anetwork connection with the second network node.
 18. The non-transitorymachine-readable medium of claim 15, wherein the flight configurationcomprises a route and a priority associated with the drone device. 19.The non-transitory machine-readable medium of claim 15, wherein thecapacity constraint of the first airspace being satisfied comprises acurrent quantity of drone devices operating in the first airspaceexceeding a defined quantity.
 20. The non-transitory machine-readablemedium of claim 15, wherein the capacity constraint is based on apriority of the unmanned aerial vehicle.